install/ostree: Set zipl as the bootloader for s390x#2152
install/ostree: Set zipl as the bootloader for s390x#2152jmarrero merged 1 commit intobootc-dev:mainfrom
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a configuration step to set 'zipl' as the bootloader for s390x architectures within the ostree repository. A review comment identifies that the configuration key used should be 'sysroot.bootloader' rather than 'bootloader' to ensure it is correctly placed in the configuration file. Additionally, it was suggested to integrate this change into the existing configuration loop to improve efficiency by avoiding an extra process execution.
bc55aeb to
f71e408
Compare
|
Right, we do the same in cosa : https://github.com/coreos/coreos-assembler/blob/main/src/osbuild-manifests/build.common.ipp.yaml#L165 |
fffc668 to
1979ad0
Compare
`zipl` cannot dynamically read BLS config at boot, and requires the MBR to be updated before. So we set `zipl` as the bootloader for s390x by default. Otherwise, s390x systems cannot reboot into new deployments. We set the ostree parameter after the initial ostree deployement because it fails if called during it. See https://github.com/coreos/coreos-assembler/blob/99bb23e7dfbfa8f1ae8b9bfaca9ff2e6d98c6cba/src/osbuild-manifests/build.common.ipp.yaml#L160-L163 Fixes bootc-dev#2151 Signed-off-by: jbtrystram <jbtrystram@redhat.com>
1979ad0 to
18196bd
Compare
|
A build with this passes coreOS tests that were failing : |
This reverts commit 90a6d6e. In 10f346e we switched rawhide to use `bootc install to-filesystem` to create our disk images. This was reverted in 90a6d6e because of s390x issues. A PR with the fix is now opened in bootc : bootc-dev/bootc#2152 and the tests denylisted in coreos#4117 so let's revert the revert to enable this again.
In coreos@10f346e we switched rawhide to use `bootc install to-filesystem` to create our disk images. This was reverted in coreos@90a6d6e a PR with the fix is now opened in bootc : bootc-dev/bootc#2152 so let's denylist those tests so we can re-enable `bootc install` for rawhide.
This reverts commit 90a6d6e. In 10f346e we switched rawhide to use `bootc install to-filesystem` to create our disk images. This was reverted in 90a6d6e because of s390x issues. A PR with the fix is now opened in bootc : bootc-dev/bootc#2152 and the tests denylisted in #4117 so let's revert the revert to enable this again.
In 10f346e we switched rawhide to use `bootc install to-filesystem` to create our disk images. This was reverted in 90a6d6e a PR with the fix is now opened in bootc : bootc-dev/bootc#2152 so let's denylist those tests so we can re-enable `bootc install` for rawhide.
cgwalters
left a comment
There was a problem hiding this comment.
Hmm...I think the real regression here might have been that we set bootloader = none unconditionally in the install logic but we should have actually let it be the default?
It may even be that since ostreedev/ostree#3104 zipl would work for the initial deployment too, but we never updated the logic to just entirely drop setting the boot loader on s390x (letting the internal ostree default work).
Anyways, since this matches what's done in cost, sounds fine to me.
ziplcannot dynamically read BLS config at boot, and requires the MBR to be updated before. So we setziplas the bootloader for s390x by default. Otherwise, s390x systems cannot reboot into new deployments.See #2151